Do It, Delegate It, or Defer It

“Do It, Delegate It, or Defer It” is a decision rule for what to do once the next action has been identified: finish a task immediately if it takes under two minutes, pass it to the appropriate person if someone else should handle it, or defer it into a Next Actions list when it takes longer and remains one’s own responsibility. Its importance lies in closing the gap between recognizing work and giving it a concrete fate, within a broader method for managing the open-ended projects and constant inputs of knowledge work.

The Three-Way Decision

The rule begins after a person has decided what the next action actually is. At that point, there are three options. An action that can be completed in less than two minutes should be done as soon as it is defined, rather than captured for later. If it will take longer, the next question is whether the person processing it is the right one to do it; if not, it should be delegated to the appropriate entity. If the person is responsible and the action exceeds the two-minute threshold, it should be deferred and tracked on one or more Next Actions lists.

The sequence distinguishes immediate completion from postponement, and postponement from transfer of responsibility. Deferring is not abandoning: it means assigning the action a place in a reminder system so it can be reconsidered and done later. Delegation likewise does not make the commitment disappear; the wider workflow depends on requests and relevant information entering the recipient’s system, being processed and organized, and becoming available for review as an option for action.

A Rule for Work Without Clear Edges

The book presents the rule against a background in which many projects have no natural endpoint. A conference, training program, compensation structure, essay, staff meeting, or reorganization could each be improved further, while the Web makes an effectively unbounded amount of potentially relevant information accessible. Work also crosses divisional boundaries, bringing more communication and shared responsibility into view. In that setting, the three options supply a small operational decision at the point where an open-ended concern becomes a specific action.

The need for such a decision is intensified by changing jobs and responsibilities, shifting organizational goals and structures, and the large volume of commitments generated both by incoming information and by agreements with oneself and others. The book argues that effective personal management must connect big-picture thinking to small open details, handle multiple levels of priority and hundreds of daily inputs, and save more time and effort than maintaining the system consumes. The three-way rule is one practical hinge in that larger design: it prevents an identified action from remaining indefinitely in an undefined state.

Reminders, Contexts, and Physical Cues

When an action is deferred, its reminder must be organized so that it can be found when it is doable. The book recommends grouping as-soon-as-possible actions by the context they require: a computer action belongs on an At Computer list, driving-related stops such as a bank or hardware store on Errands, and a face-to-face conversation with a partner in an Emily folder or list. The needed level of detail depends on how many actions are being tracked and how often a person moves between contexts. With only twenty-five actions, one list may suffice; with fifty or a hundred, a single undifferentiated list makes selection harder and forces repeated sorting.

Context-based organization also compels a decision about the next physical action. A person must identify whether an item requires a computer, a phone, or being in a store before placing it on the appropriate list. At the moment of choosing work, the same principle asks what can be done where the person is and with the tools available. A context-sorted list narrows the options to actions that can actually be undertaken, rather than repeatedly reconsidering unavailable ones.

The book also illustrates the logic of reminders with a physical trick: someone who must bring work home the next morning can put it in front of the door or on their keys. The placement lets the more deliberate person the night before compensate for the less alert person in the morning. The author calls this Put It in Front of the Door, extending the household cue into a metaphor for placing reminders at the door of the mind. The rule’s immediate-do, delegate, or defer decision and these later cues serve related but distinct purposes: one assigns an action a disposition, while the other helps bring a deferred commitment back to attention at the right time.

Individual Systems and Shared Commitments

The method depends on reliable handling of communications across people as well as on individual lists. A request sent by voice-mail, e-mail, conversation, or written note must reach the recipient’s system, be processed and organized, and remain available for review. If a person reliably manages only one medium, colleagues may be forced to use that channel, hindering coordination. The book treats dulled responsiveness as a weak link: initiatives cannot be trusted to proceed if communications routinely fail to enter a usable system.

Organizations cannot prescribe a single personal system for everyone, but they can hold people accountable for outcomes and for tracking what comes their way. They also need a culture in which people can have more work than they can complete and can continually renegotiate agreements about what will not be done. That renegotiation requires reliable collection and tracking: commitments that have been forgotten cannot be reconsidered with oneself or with others. In this wider context, the three-way rule is not a promise that every task will be completed. It is a means of deciding what happens to each identified action, so that work can be done, entrusted to someone else, or deliberately retained for later rather than lost among the inputs.